tester3 2.2.0
Loading...
Searching...
No Matches
tester3


Tester 3 Click

Tester 3 Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.


Click Library

  • Author : Stefan Filipovic
  • Date : May 2026.
  • Type : GPIO type

Software Support

Example Description

This example demonstrates the use of Tester 3 Click board by controlling all LEDs on the Click board together and in sequential pin toggling with different delays.

Example Libraries

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.Tester3

Example Key Functions

  • tester3_cfg_setup This function initializes Click configuration structure to initial values.
    void tester3_cfg_setup(tester3_cfg_t *cfg)
    Tester 3 configuration object setup function.
    Tester 3 Click configuration object.
    Definition tester3.h:115
  • tester3_init This function initializes all necessary pins and peripherals used for this Click board.
    err_t tester3_init ( tester3_t *ctx, tester3_cfg_t *cfg );
    err_t tester3_init(tester3_t *ctx, tester3_cfg_t *cfg)
    Tester 3 initialization function.
    Tester 3 Click context object.
    Definition tester3.h:94
  • tester3_toggle_all This function toggles all mikroBUS pins together a desired number of times with the selected delay between each toggle.
    void tester3_toggle_all ( tester3_t *ctx, uint16_t num_toggles, uint16_t toggle_delay_ms );
    void tester3_toggle_all(tester3_t *ctx, uint16_t num_toggles, uint16_t toggle_delay_ms)
    Tester 3 toggle all function.
  • tester3_toggle_seq This function toggles all mikroBUS pins one by one with the selected delay between each toggle.
    void tester3_toggle_seq ( tester3_t *ctx, uint16_t toggle_delay_ms );
    void tester3_toggle_seq(tester3_t *ctx, uint16_t toggle_delay_ms)
    Tester 3 toggle seq function.

Application Init

Initializes the driver and logger.

void application_init ( void )
{
log_cfg_t log_cfg;
tester3_cfg_t tester3_cfg;
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
// Click initialization.
tester3_cfg_setup( &tester3_cfg );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == tester3_init( &tester3, &tester3_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
#define TESTER3_MAP_MIKROBUS(cfg, mikrobus)
MikroBUS pin mapping.
Definition tester3.h:72
void application_init(void)
Definition main.c:33
#define MIKROBUS_POSITION_TESTER3
Definition main.c:27

Application Task

Toggles all pins together 5 times with a 500ms delay between each toggle, then toggles each pin sequentially with a 300ms delay between toggling each pin.

void application_task ( void )
{
log_printf( &logger, " Toggling all pins together 5 times with 500ms delay\r\n\n" );
tester3_toggle_all ( &tester3, 5, 500 );
log_printf( &logger, " Toggling all pins sequentially with 300ms delay\r\n\n" );
tester3_toggle_seq ( &tester3, 300 );
}
void application_task(void)
Definition main.c:63

Application Output

This Click board can be interfaced and monitored in two ways:

  • Application Output - Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
  • UART Terminal - Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.

Additional Notes and Information

The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.